Repository navigation
ci: check the supply chain - #3
Open
DroBov1Tya wants to merge 1 commit into
Open
DroBov1Tya wants to merge 1 commit into
DroBov1Tya wants to merge 1 commit into
Conversation
The baseline asks for cargo-deny, osv-scanner, secret scanning, SBOMs and pinned tools; CI had none of them, and releases were built by whatever stable Rust was current, not the 1.99.1 CI tests with. - deny job and deny.toml: RustSec advisories (vulnerable and yanked crates fail; unmaintained fails for direct dependencies), a permissive license allowlist plus MPL-2.0, no wildcards, crates.io as the only source. - osv job and osv-scanner.toml: osv.dev over every lockfile, with the same exceptions as deny.toml, each dated so it is reviewed again. - secrets job and .gitleaksignore: gitleaks over the full history; three known false positives (a public key, the RFC 6455 sample nonce). - web job builds the wasm client with scripts/build-web.sh as releases do; check gains a Linux arm64 runner. - Scanners are release binaries checked against a SHA-256 in the workflow, not third-party actions. - dependabot: weekly grouped cargo and actions updates, small PR limits. - release: toolchain 1.99.1 everywhere; an sbom job uploads CycloneDX SBOMs of the terminal, web and desktop programs. Two advisories are ignored with reasons in deny.toml and need their own changes: RUSTSEC-2026-0462 (rmcp < 3.9.0, fix by cargo update -p rmcp) and RUSTSEC-2026-0459 (bundled SQLite, needs a sqlx release). Not verified: no workflow ran on GitHub (actionlint not run); the Linux downloads were hash-checked locally but not executed; the arm64 check, the web job's cargo install path and the sbom upload did not run; dependabot config not validated by GitHub. Ran locally: cargo deny check (pass), osv-scanner 2.7.0 (pass with osv-scanner.toml), gitleaks 8.30.1 over the history (pass with .gitleaksignore), scripts/build-web.sh (pass), cargo-cyclonedx 0.5.9 SBOM step (pass), YAML parse and changelog check.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes the supply-chain gaps of the project's security baseline:
Ignored with reasons and expiry: RUSTSEC-2026-0462 (rmcp DoS, fix is cargo update -p rmcp, to land next), RUSTSEC-2026-0459 (bundled SQLite, waits on sqlx), chrono unmaintained.
Not verified: no workflow has run on GitHub yet; actionlint not run.